The log attachments in Sentry only contain the logs from the failed pod, not all pods. Very often it's the bootloader that's failed, but the bootloader logs don't say anything interesting – they just say the bootloader can't connect to the DB. So this PR would attach all logs from platform pods (only on airbyte chart failure) which hopefully gives us something more interesting to look at.

Java log parse code gets removed

The code I wrote to try to parse java logs from the platform in diagnoseAirbyteChartFailure is mostly a failure. Most of the time it just returns

unable to install airbyte chart: pod airbyte-abctl-airbyte-bootloader: unknown

There are a few variants in the telemetry, such as:

unable to install airbyte chart: pod airbyte-abctl-airbyte-bootloader: Caused by: io.airbyte.db.check.DatabaseCheckException: Unable to connect to the database.

unable to install airbyte chart: pod airbyte-abctl-airbyte-bootloader: Caused by: io.micronaut.context.exceptions.ConfigurationException: Could not resolve placeholder ${DATABASE_PASSWORD}

unable to install airbyte chart: pod airbyte-abctl-airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: ERROR: type "refresh_type" already exists

unable to install airbyte chart: pod airbyte-abctl-airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: ERROR: must be owner of table airbyte_configs

These don't seem very clear for the user. The code to parse java logs lines is clunky and broken and not clearly valuable, so I've removed it in this PR. When the bootloader is the only failed pod, I return an error with a help message that says to run again with --verbose to see the full bootloader logs.